Call Detail Records

Call Detail Records (CDR) contain vital statistics and information on calls processed by the device. The device can generate and report CDRs at various stages of the call (e.g., start of call or end of call). CDRs can be generated for SIP signaling and media.

You can configure the device to generate and report CDRs for the following call stages:

■

Call start: The device sends a SIP INVITE request to the call leg.

■

Call connect: The call leg answers the call (SIP 200 OK).

■

Call end: An established call ends (SIP BYE message), or a call leg that never became established ends, for example, because the call was routed to an alternate destination or forked to multiple destinations.

The device generates a CDR for each call leg:

■

Incoming call leg

■

Outgoing call leg

If the outgoing leg includes multiple destinations (legs), for example, with alternate routing or call forking, the device generates a CDR for each destination, even if the destination is canceled or fails. For example, assume the device receives an incoming call from A, forks it to destinations B and C, and establishes the call with C. The device generates the following CDRs for these legs:

●

Call Start CDRs are generated for A, B, and C.

●

Call Connect CDRs are generated for A and C.

●

Call End CDRs are generated for A, B, and C.

The device can send CDRs to any of the following:

■

Syslog server: The CDR Syslog message complies with RFC 3164 and is identified by Facility 17 ("local1") and Severity 5 (Notice).

■

RADIUS server: For CDR in RADIUS format, see Configuring RADIUS Accounting. To configure RADIUS servers for CDR reporting, see Configuring RADIUS Servers.

■

REST server: The device can send signaling-related CDRs to a REST server using AudioCodesREST API (see Configuring CDR Reporting to REST Server).

■

Locally on the device: CDRs can be stored locally on the device (see Storing CDRs Locally on the Device).